-
Notifications
You must be signed in to change notification settings - Fork 154
chore(deps): update nuxt framework to ^3.17.2 - autoclosed #415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for n3-supabase canceled.
|
e922760 to
97a77e5
Compare
97a77e5 to
32cca22
Compare
cbe4a57 to
5bf6cb4
Compare
5bf6cb4 to
573337a
Compare
deea9da to
6e7f24b
Compare
6e7f24b to
1ea4f8d
Compare
1ea4f8d to
12f5758
Compare
12f5758 to
8900a47
Compare
8900a47 to
935daad
Compare
935daad to
213c243
Compare
239dbda to
bcfd4c5
Compare
bcfd4c5 to
71cbba2
Compare
71cbba2 to
6e6bc6f
Compare
6e6bc6f to
36d8ff2
Compare
36d8ff2 to
0d17528
Compare
0d17528 to
6520f69
Compare
6520f69 to
93ce55d
Compare
93ce55d to
bcfcc0f
Compare
bcfcc0f to
df741fb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^3.15.4->^3.17.2^3.15.4->^3.17.2Release Notes
nuxt/nuxt (@nuxt/kit)
v3.17.2Compare Source
✅ Upgrading
Our recommendation for upgrading is to run:
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
handleHotUpdatein production (#31971)🩹 Fixes
transition(#31945)useFetch(#31963)scrollToTop(#31914)vfseven if a file exists inbuildDir(#31969)useAsyncDatareactive tokeychanges whenimmediate: false(#31987)WarningFiltertype (2a79dbd68)warningIgnoreFilters(a62e808ac)📖 Documentation
@nuxt/kitdocumentation (#31793)🏡 Chore
✅ Tests
asyncDataDefaults.value(91568c5da)🤖 CI
❤️ Contributors
v3.17.1Compare Source
✅ Upgrading
Our recommendation for upgrading is to run:
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🩹 Fixes
executewhen non-immediate fetch key changes (#31941)escapeHTMLfrom vue (8e4b8d62f)@vue/shareddependency (7d445c963)📦 Build
🏡 Chore
✅ Tests
❤️ Contributors
v3.17.0Compare Source
👀 Highlights
This release brings a major reworking of the async data layer, a new built-in component, better warnings, and performance improvements!
📊 Data Fetching Improvements
A major reorganization of Nuxt's data fetching layer brings significant improvements to
useAsyncDataanduseFetch.Although we have aimed to maintain backward compatibility and put breaking changes behind the
experimental.granularCachedDataflag (disabled by default), we recommend testing your application thoroughly after upgrading. You can also disableexperimental.purgeCachedDatato revert to the previous behavior if you are relying on cached data being available indefinitely after components usinguseAsyncDataare unmounted.👉 Read the the original PR for full details (#31373), but here are a few highlights.
Consistent Data Across Components
All calls to
useAsyncDataoruseFetchwith the same key now share the underlying refs, ensuring consistency across your application:This solves various issues where components could have inconsistent data states.
Reactive Keys
You can now use computed refs, plain refs, or getter functions as keys:
Optimized Data Refetching
Multiple components watching the same data source will now trigger only a single data fetch when dependencies change:
🎭 Built-In Nuxt Components
<NuxtTime>- A new component for safe time displayWe've added a new
<NuxtTime>component for SSR-safe time display, which resolves hydration mismatches when working with dates (#31876):The component accepts multiple time formats and gracefully handles both client and server rendering.
Enhanced
<NuxtErrorBoundary>The
<NuxtErrorBoundary>component has been converted to a Single File Component and now exposeserrorandclearErrorfrom the component - as well as in the error slot types, giving you greater ability to handle errors in your templates and viauseTemplateRef(#31847):🔗 Router Improvements
<NuxtLink>now accepts atrailingSlashprop, giving you more control over URL formatting (#31820):🔄 Loading Indicator Customization
You can now customize the loading indicator with new props directly on the component (#31532):
hideDelay: Controls how long to wait before hiding the loading barresetDelay: Controls how long to wait before resetting loading indicator state📚 Documentation as a Package
The Nuxt documentation is now available as an npm package! You can install
@nuxt/docsto access the raw markdown and YAML content used to build the documentation website (#31353).💻 Developer Experience Improvements
We've added several warnings to help catch common mistakes:
runtimeConfig.appnamespace #31774definePageMetais used more than once in a file #31634🔌 Enhanced Module Development
Module authors will be happy to know:
experimental.enforceModuleCompatibilityallows Nuxt to throw an error when a module is loaded that isn't compatible with it (#31657). It will be enabled by default in Nuxt v4.addComponentExports#27155🔥 Performance Improvements
Several performance improvements have been made:
tinyglobbyfor faster file globbing #31668.datadirectory from type-checking for faster builds #31738purgeCachedDatacheck #31785✅ Upgrading
Our recommendation for upgrading is to run:
This refreshes your lockfile and pulls in all the latest dependencies that Nuxt relies on, especially from the unjs ecosystem.
👉 Changelog
compare changes
🚀 Enhancements
hideDelayandresetDelayprops for loading indicator (#31532)@nuxt/docs(#31353)loadNuxtConfigto nitro (#31680)runtimeConfig.appnamespace (#31774)middlewarewhen scanning page metadata (#30708)addComponentExports(#27155)<NuxtErrorBoundary>to SFC + exposeerror/clearError(#31847)<NuxtTime>component for ssr-safe time display (#31876)trailingSlashprop to<NuxtLink>(#31820)🔥 Performance
tinyglobby(#31668).datadirectory from type-checking (#31738)purgeCachedDatacheck to improve tree-shaking (#31785)oxc-parsermanual wasm fallback logic (#31484)🩹 Fixes
modulesDirpaths are added tofs.allow(#31540)/_nuxt/(#31646)useLazyAsyncData(#31676)error.url(#31679)app:renderedis called (#31686)fallbackattribute when stripping<DevOnly>(c1d735c27)noScripts(c9572e953)compatibilityDate(#31725)statusMessagewhen rendering html error (#31761)definePageMetais used more than once (#31634)error.databefore renderingerror.vue(#31571)useAsyncDatain console log (#31801)NuxtErrorBoundaryerror (#31791)preserveModules(#31839)pendingwithstatusvalue for v4 (#25864)nuxt/appin generated middleware and layouts declarations (#31808)withoutBase(f956407bb)vuein vite-node dev server (f3882e004)tsconfig.json(#31882)useNuxtData(#31893)useFetchwatch sources (#31903)modulesDirto store build cache files (#31907)💅 Refactors
shallowReffor primitives as well (#31662)_replaceAppConfigwhen applying hmr (#31786)ConfigSchema(#31894)📖 Documentation
app.vue(#31645)templateParamsto seo docs (#31583)useHydration(#31712)callOncereturning value (#31747)vs.consistently (#31760)addServerHandlerexample (#31769)📦 Build
vue-sfc-transformerto process sfcs (#31691)🏡 Chore
✅ Tests
<NuxtErrorBoundary>(4df92c45f)pendingWhenIdle(08f2224c8)🤖 CI
❤️ Contributors
v3.16.2Compare Source
✅ Upgrading
Our recommendation for upgrading is to run:
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
useRequestEventon client (#31586)🩹 Fixes
<Body>and<Html>(#31513)/indexis the last segment (#31528)page:loading:endhook before navigation (#31504)document.cookie(#31517)resolveComponent(#31526)_nuxt/paths in development (#31543)error.vue(#31573)unheadv2 api in default welcome + error pages (#31584)scanPageMetais disabled (0ba454b21)💅 Refactors
<NuxtPage>(#31561)useServerHeadinonPrehydratewithuseHead(#31585)📖 Documentation
useTemplateRef(#31458)$fetch(#31459)dedupeflag (#31467)refreshNuxtDatadocs (#31448)--before--template(#31469)resolveComponentonly auto-imports components with literal strings (#31511)tsconfig.json(#31473)page:startandpage:finishhooks (#31570)🏡 Chore
✅ Tests
❤️ Contributors
v3.16.1Compare Source
compare changes
🔥 Performance
🩹 Fixes
mocked-exports(#31295)typedPagesimplementation (#31331)📖 Documentation
app.headexample (#31350)addServerTemplateto modules guide (#31369)rspackand removetest-utilsfor monorepo guide (#31371)inisyntax block highlighting for.envfiles (f79fabe46)useHydrationdocs (#31427)🏡 Chore
✅ Tests
srvxand random port for remote provider (#31432)🤖 CI
❤️ Contributors
v3.16.0Compare Source
👀 Highlights
There's a lot in this one!
⚡️ A New New Nuxt
Say hello to
create-nuxt, a new tool for starting Nuxt projects (big thanks to @devgar for donating the package name)!It's a streamlined version of
nuxi init- just a sixth of the size and bundled as a single file with all dependencies inlined, to get you going as fast as possible.Starting a new project is as simple as:
Special thanks to @cmang for the beautiful ASCII-art. ❤️
Want to learn more about where we're headed with the Nuxt CLI? Check out our roadmap here, including our plans for an interactive modules selector.
🚀 Unhead v2
We've upgraded to
unheadv2, the engine behind Nuxt's<head>management. This major version removes deprecations and improves how context works:If you're using Unhead directly in your app, keep in mind:
#app/composables/headinstead of@unhead/vue@unhead/vuemight lose async contextDon't worry though - we've maintained backward compatibility in Nuxt 3, so most users won't need to change anything!
If you've opted into
compatibilityVersion: 4, check out our upgrade guide for additional changes.🔧 Devtools v2 Upgrade
Nuxt Devtools has leveled up to v2 (#30889)!
You'll love the new features like custom editor selection, Discovery.js for inspecting resolved configs (perfect for debugging), the return of the schema generator, and slimmer dependencies.
One of our favorite improvements is the ability to track how modules modify your Nuxt configuration - giving you X-ray vision into what's happening under the hood.
👉 Discover all the details in the Nuxt DevTools release notes.
⚡️ Performance Improvements
We're continuing to make Nuxt faster, and there are a number of improvements in v3.16:
exsolvefor module resolution (#31124) along with the rest of the unjs ecosystem (nitro, c12, pkg-types, and more) - which dramatically speeds up module resolutionloadNuxtby skipping unnecessary resolution steps (#31176) - faster startupsoxc-parserfor parsing in Nuxt plugins (#30066)All these speed boosts happen automatically - no configuration needed!
Shout out to CodSpeed with Vitest benchmarking to measure these improvements in CI - it has been really helpful.
To add some anecdotal evidence, my personal site at roe.dev loads 32% faster with v3.16, and nuxt.com is 28% faster. I hope you see similar results! ⚡️
🕰️ Delayed Hydration Support
We're very pleased to bring you native delayed/lazy hydration support (#26468)! This lets you control exactly when components hydrate, which can improve initial load performance and time-to-interactive. We're leveraging Vue's built-in hydration strategies - check them out in the Vue docs.
You can also listen for when hydration happens with the
@hydratedevent:Learn more about lazy hydration in our components documentation.
🧩 Advanced Pages Configuration
You can now fine-tune which files Nuxt scans for pages (#31090), giving you more control over your project structure:
🔍 Enhanced Debugging
We've made debugging with the
debugoption more flexible! Now you can enable just the debug logs you need (#30578):Or keep it simple with
debug: trueto enable all these debugging features.🎨 Decorators Support
For the decorator fans out there (whoever you are!), we've added experimental support (#27672). As with all experimental features, feedback is much appreciated.
📛 Named Layer Aliases
It's been much requested, and it's here! Auto-scanned local layers (from your
~~/layersdirectory) now automatically create aliases. You can access your~~/layers/testlayer via#layers/test(#30948) - no configuration needed.If you want named aliases for other layers, you can add a name to your layer configuration:
This creates the alias
#layers/example-layerpointing to your layer - making imports cleaner and more intuitive.🧪 Error Handling Improvements
We've greatly improved error messages and source tracking (#31144):
useAsyncDatacalls with precise file location informationPlus, we're now using Nitro's beautiful error handling (powered by youch) to provide more helpful error messages in the terminal, complete with stacktrace support.
Nitro now also automatically applies source maps without requiring extra Node options, and we set appropriate security headers when rendering error pages.
📦 Module Development Improvements
For module authors, we've added the ability to augment Nitro types with
addTypeTemplate(#31079):⚙️ Nitro v2.11 Upgrade
We've upgraded to Nitro v2.11. There are so many improvements - more than I can cover in these brief release notes.
👉 Check out all the details in the Nitro v2.11.0 release notes.
📦 New
unjsMajor VersionsThis release includes several major version upgrades from the unjs ecosystem, focused on performance and smaller bundle sizes through ESM-only distributions:
✅ Upgrading
As usual, our recommendation for upgrading is to run:
This refreshes your lockfile and pulls in all the latest dependencies that Nuxt relies on, especially from the unjs ecosystem.
👉 Changelog
compare changes
🚀 Enhancements
@nuxt/devtoolsto v2 (#30889)NuxtPage(#30704)directoryToURLto normalise paths (#30986)start/setin loading indicator (#30989)pages/(#31090)NuxtLinkslot (#31104)addTypeTemplate(#31079)oxc-parserinstead of esbuild + acorn (#30066)🔥 Performance
exsolvefor module resolution (#31124)loadNuxt(#31176)🩹 Fixes
<NuxtLayout>fallbackprop is typed (#30832)keepalivecache reset (#30807)divwrapper in client-only pages (#30425)nitropack(aba75bd5a)nullfrom resolve functions (d68e8ce57)app.head.metavalues are undefined (#30959)shared/directories available within layers (#30843)<pre>when rendering dev errors (9aab69ec4)page:transition:starttype (#31040)provide/injectwork insetupofdefineNuxtComponent(#30982)_for NuxtIsland name on server pages (#31072)ohashto calculate legacy async data key without hash (#31087)shareddir from config (#31091)nuxt.options.pagesto detected configuration (#31101)definePageMetadoes not receive an object (#31156)no-ssrmiddleware handler (a99c59fbd)navigatewithvue-router(7a1934509)nuxt.options.pages(fa480e0a0)resolveModule(6fb5c9c15)resolveTypePath(a0f9ddfe2)compilerOptions.paths(835e89404)RawVueCompilerOptionsfor unresolvedtsconfig(#31202)Configuration
📅 Schedule: Branch creation - Every minute ( * * * * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.